Handle a mergedBy NaN value#165
Conversation
This avoids a TypeError when retrieving PRs that have not been merged, which was causing a critical error. From where mergedBy is set, it can be a pandas na or it can be a username. Fixes executablebooks#164
|
What is weird to me is that this seems to only have recently started failing. Why did things pass before? |
Some upstream version differences? |
It would be |
|
hah I just ran into this in myst-theme - let's make a release so we get this fix out |
Yep, comparing the logs between a failing and succeeding run, the difference is pandas 3.0 is in the failing run, pandas 2.3.3 in the run that succeeded. |
|
I bet it's that there is a new str type, where the missing value is always NaN. I bet before it was None, which is falsey, but NaN is truthy, so that boolean check used to work, but now failed. According to the migration guide, the correct fix is to use pd.isna (or notna for the opposite check), so I think this PR does the correct thing. |
+1 - this is blocking us making a jupyterlab release |
|
release is already out in the wild! |
|
And our CI tests are now passing with 1.1.5. Thanks! |
This avoids a TypeError when retrieving PRs that have not been merged, which was causing a critical error. From where mergedBy is set, it can be a pandas na or it can be a username.
Fixes #164
To reproduce:
Error: